home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat3 / Xm / XmCvtXmStringToCT.z / XmCvtXmStringToCT
Text File  |  1998-10-30  |  6KB  |  133 lines
  1.  
  2.  
  3.  
  4.      XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT((((3333XXXX))))     UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV     XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT((((3333XXXX))))
  5.  
  6.  
  7.  
  8.      NNNNAAAAMMMMEEEE
  9.           XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT - A compound string function that converts
  10.           a compound string to compound text
  11.  
  12.      SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.           #include <Xm/Xm.h>
  14.           cccchhhhaaaarrrr **** XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT(
  15.           XXXXmmmmSSSSttttrrrriiiinnnngggg ssssttttrrrriiiinnnngggg);
  16.  
  17.      VVVVEEEERRRRSSSSIIIIOOOONNNN
  18.           This page documents Motif 2.1.
  19.  
  20.      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  21.           XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT converts a compound string to a (cccchhhhaaaarrrr ****)
  22.           string in compound text format.  The application must call
  23.           XXXXttttAAAAppppppppIIIInnnniiiittttiiiiaaaalllliiiizzzzeeee before calling this function.  The converter
  24.           uses the font list tag associated with a given compound
  25.           string segment to select a compound text format for that
  26.           segment.  A registry defines a mapping between font list
  27.           tags and compound text encoding formats.  The converter uses
  28.           the following algorithm for each compound string segment:
  29.  
  30.              1. If the compound string segment tag is mapped to
  31.                 XXXXmmmmFFFFOOOONNNNTTTTLLLLIIIISSSSTTTT____DDDDEEEEFFFFAAAAUUUULLLLTTTT____TTTTAAAAGGGG in the registry, the converter
  32.                 passes the text of the compound string segment to
  33.                 XXXXmmmmbbbbTTTTeeeexxxxttttLLLLiiiissssttttTTTTooooTTTTeeeexxxxttttPPPPrrrrooooppppeeeerrrrttttyyyywith an encoding style of
  34.                 XXXXCCCCoooommmmppppoooouuuunnnnddddTTTTeeeexxxxttttSSSSttttyyyylllleeee and uses the resulting compound
  35.                 text for that segment.
  36.  
  37.              2. If the compound string segment tag is mapped to an MIT
  38.                 registered charset in the registry, the converter
  39.                 creates the compound text for that segment using the
  40.                 charset (from the registry) and the text of the
  41.                 compound string segment as defined in the X Consortium
  42.                 Standard _C_o_m_p_o_u_n_d _T_e_x_t _E_n_c_o_d_i_n_g.
  43.  
  44.              3. If the compound string segment tag is mapped to a
  45.                 charset in the registry that is neither
  46.                 XXXXmmmmFFFFOOOONNNNTTTTLLLLIIIISSSSTTTT____DDDDEEEEFFFFAAAAUUUULLLLTTTT____TTTTAAAAGGGG nor an MIT registered charset,
  47.                 the converter creates the compound text for that
  48.                 segment using the charset (from the registry) and the
  49.                 text of the compound string segment as an "extended
  50.                 segment" with a variable number of octets per
  51.                 character.
  52.  
  53.              4. If the compound string segment tag is not mapped in
  54.                 the registry, the result is implementation dependent.
  55.  
  56.           _s_t_r_i_n_g    Specifies a compound string to be converted to
  57.                     compound text.
  58.  
  59.      RRRREEEETTTTUUUURRRRNNNN
  60.  
  61.  
  62.  
  63.      PPPPaaaaggggeeee 1111                                         ((((pppprrrriiiinnnntttteeeedddd 11110000////22224444////99998888))))
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70.      XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT((((3333XXXX))))     UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV     XXXXmmmmCCCCvvvvttttXXXXmmmmSSSSttttrrrriiiinnnnggggTTTTooooCCCCTTTT((((3333XXXX))))
  71.  
  72.  
  73.  
  74.           Returns a (cccchhhhaaaarrrr ****) string in compound text format.  This
  75.           format is described in the X Consortium Standard _C_o_m_p_o_u_n_d
  76.           _T_e_x_t _E_n_c_o_d_i_n_g.  The function allocates space to hold the
  77.           returned string.  The application is responsible for
  78.           managing the allocated space.  The application can recover
  79.           the allocated space by calling XXXXttttFFFFrrrreeeeeeee.
  80.  
  81.      RRRREEEELLLLAAAATTTTEEEEDDDD
  82.           XXXXmmmmCCCCvvvvttttCCCCTTTTTTTTooooXXXXmmmmSSSSttttrrrriiiinnnngggg(3), XXXXmmmmFFFFoooonnnnttttLLLLiiiisssstttt(3),
  83.           XXXXmmmmMMMMaaaappppSSSSeeeeggggmmmmeeeennnnttttEEEEnnnnccccooooddddiiiinnnngggg(3), XXXXmmmmRRRReeeeggggiiiisssstttteeeerrrrSSSSeeeeggggmmmmeeeennnnttttEEEEnnnnccccooooddddiiiinnnngggg(3), and
  84.           XXXXmmmmSSSSttttrrrriiiinnnngggg.
  85.  
  86.  
  87.  
  88.  
  89.  
  90.  
  91.  
  92.  
  93.  
  94.  
  95.  
  96.  
  97.  
  98.  
  99.  
  100.  
  101.  
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.      Page 2                                         (printed 10/24/98)
  130.  
  131.  
  132.  
  133.